Summary

According to the rust documentation , std::mem::transmute is a dangerous function that is very prone to creating undefined behavior and should only be used as a last resort:

Both the argument and the result must be valid at their given type.
Violating this condition leads to undefined behavior.
The compiler will generate code assuming that you, the programmer, ensure that there will never be undefined behavior.
It is therefore your responsibility to guarantee that every value passed to transmute is valid at both types Src and Dst.
Failing to uphold this condition may lead to unexpected and unstable compilation results.
This makes transmute incredibly unsafe. transmute should be the absolute last resort.

And all the transmute functions used so far in this project are simply being used to extend the lifetime of a boxed value. This scenario is common in FFI code, so there are already better functions than std::mem::transmute for this. For example, you can use the pair Box::into_raw and Box::from_raw.

This pull request replaces all std::mem::transmute calls with Box::into_raw and Box::from_raw to make the code safer.

Note

• All commits must be signed to be merged
• CI must be passed to be merged